LBNs Prefetching Per CPU

ABSTRACT

The present disclosure generally relates to prefetching data from one or more CPUs prior to the data being requested by a host device. The prefetched data is prefetched from memory and stored in cache. If a host device requests data that is not already in cache, then a determination is made regarding whether the data is scheduled to be written into cache. If the data is not in cache and is not scheduled to be written into cache, then the data is retrieved from memory and delivered to the host device. If the data is scheduled to be written into cache, or is currently being written into cache, then the request to retrieve the data is delayed or scheduled to retrieve the data once the data is in cache. If the data is already in cache, the data is delivered to the host device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a divisional of U.S. patent application Ser. No.16/748,790, filed Jan. 21, 2020, which application is a divisional ofU.S. patent application Ser. No. 15/474,340, filed Mar. 30, 2017, nowU.S. Pat. No. 10,565,115, each of which is herein incorporated byreference.

BACKGROUND OF THE DISCLOSURE Field of the Disclosure

Embodiments of the present disclosure generally relate to a method andapparatus for prefetching data into cache memory prior to receiving arequest for the data from a host device.

Description of the Related Art

In a multiprocessor hard drive or SSD environment, multiple processorsare used to simultaneously prefetch data needed for expected futurereads by the host into memory. To do so, a “master” processor may assignwhich processors will prefetch desired ranges so that multipleprocessors are not reading the same data from the disk or NAND, whichwould result in unresolvable collisions if allowed. Alternatively, thedifferent processors may be hardcoded with different ranges in thefirmware code.

The data is typically read from the disk or NAND at the LBN granularity.However, the host can request the data to be read at the LBAgranularity, which is a subset of the LBN. Due to this, it is possiblethat the host, in a single command, will request data that overlaps theprefetch range of two different processors, which is not optimal asadditional overhead will be needed to move all of the data to oneprocessor before the data is returned to the host.

As an example, if the prefetching engine predicts that the host issending commands sequentially with a length of 6 LBNs, two differentprocessors may have LBNs prefetched with the first processor having LBNs1-3 and the second processor having LBNs 4-6. LBNs 1-3 have LBAs 1-299while LBNs 4-6 have LBAs 300-599. If the host device starts reading atLBA 275 and reads sequentially for one LBN, then the host will attemptto read LBAs 275-325. However, these LBAs span LBNs 3 and 4, which willcause an issue because the LBNs are cached on two different processors.

Therefore, there is a need in the art to prefetch data in a moreefficient manner.

SUMMARY OF THE DISCLOSURE

The present disclosure generally relates to prefetching data from one ormore CPUs prior to the data being requested by a host device. Theprefetched data is prefetched from memory and stored in cache. If a hostdevice requests data that is not already in cache, then a determinationis made regarding whether the data is scheduled to be written intocache. If the data is not in cache and is not scheduled to be writteninto cache, then the data is retrieved from memory and delivered to thehost device. If the data is scheduled to be written into cache, or iscurrently being written into cache, then the request to retrieve thedata is delayed or scheduled to retrieve the data once the data is incache. If the data is already in cache, the data is delivered to thehost device. It is to be understood that while the examples disclosedherein are in reference to NAND memory, the embodiments herein areequally applicable to hard disk drive (HDD) storage as well.

In one embodiment, a system comprises a host device and a memory systemcoupled to the host device. The memory system comprises: a first CPU; atleast one additional CPU; and a memory device coupled to both the firstCPU and the at least one additional CPU. The system also comprises meansto determine an amount of LBNs to prefetch and to cause the amount ofLBNs to be prefetched and written into cache.

In another embodiment, a method comprises receiving a first request froma host device to read first data and a second request to read seconddata from a memory device that is coupled to a plurality of CPUs,wherein a first CPU of the plurality of CPUs has a cache storage;reading the first data from the memory device using the first CPU;reading the second data from the memory device using a second CPU of theplurality of CPUs; writing the first data and the second data to thecache storage; reading the first and second data from the cache storage;and delivering the first and second data to the host device.

In another embodiment, a method comprises receiving a first request froma host device to read first LBA data from a plurality of LBNs disposedin a memory device that is coupled to a plurality of CPUs, wherein afirst CPU of the plurality of CPUs has a cache storage; reading a firstportion of the first LBA data from one or more first LBNs of the memorydevice; reading a second portion of the first LBA data from one or moresecond LBNs of the memory device; writing the one or more first LBNsdata and the one or more second LBNs data to the cache storage; readingthe first LBA data from the cache storage; and delivering the first LBAdata to the host device.

In another embodiment, a method comprises prefetching and storing afirst predetermined number of LBNs in a cache of a first CPU; readingdata from the cache; delivering the data to a host device; andprefetching and storing a second number of LBNs into the cache, whereinthe retrieving and storing occurs prior to receiving a request from thehost device to read the data.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the manner in which the above recited features of the presentdisclosure can be understood in detail, a more particular description ofthe disclosure, briefly summarized above, may be had by reference toembodiments, some of which are illustrated in the appended drawings. Itis to be noted, however, that the appended drawings illustrate onlytypical embodiments of this disclosure and are therefore not to beconsidered limiting of its scope, for the disclosure may admit to otherequally effective embodiments.

FIG. 1 is a schematic illustration of a system according to oneembodiment.

FIGS. 2A and 2B are schematic illustrations of CPUs of the system ofFIG. 1.

FIG. 3 is a flowchart illustrating a method according to one embodiment.

FIG. 4 is a flowchart illustrating a method according to anotherembodiment.

FIG. 5 is a flowchart illustrating a method according to anotherembodiment.

To facilitate understanding, identical reference numerals have beenused, where possible, to designate identical elements that are common tothe figures. It is contemplated that elements disclosed in oneembodiment may be beneficially utilized on other embodiments withoutspecific recitation.

DETAILED DESCRIPTION

In the following, reference is made to embodiments of the disclosure.However, it should be understood that the disclosure is not limited tospecific described embodiments. Instead, any combination of thefollowing features and elements, whether related to differentembodiments or not, is contemplated to implement and practice thedisclosure. Furthermore, although embodiments of the disclosure mayachieve advantages over other possible solutions and/or over the priorart, whether or not a particular advantage is achieved by a givenembodiment is not limiting of the disclosure. Thus, the followingaspects, features, embodiments and advantages are merely illustrativeand are not considered elements or limitations of the appended claimsexcept where explicitly recited in a claim(s). Likewise, reference to“the disclosure” shall not be construed as a generalization of anyinventive subject matter disclosed herein and shall not be considered tobe an element or limitation of the appended claims except whereexplicitly recited in a claim(s). It is to be understood that whilereference will be made to NAND or hard disk drives, the disclosure isequally applicable to other types of no-volatile memory as well.

The present disclosure generally relates to prefetching data from one ormore CPUs prior to the data being requested by a host device. Theprefetched data is prefetched from memory and stored in cache. If a hostdevice requests data that is not already in cache, then a determinationis made regarding whether the data is scheduled to be written intocache. If the data is not in cache and is not scheduled to be writteninto cache, then the data is retrieved from memory and delivered to thehost device. If the data is scheduled to be written into cache, or iscurrently being written into cache, then the request to retrieve thedata is delayed or scheduled to retrieve the data once the data is incache. If the data is already in cache, the data is delivered to thehost device.

FIG. 1 is a schematic illustration of a system 100 according to oneembodiment. The system includes a host device 102 that interacts with amemory system 104. A controller 106 coupled to both the host device 102and the memory system 104. The memory system stores data that may beneeded by the host device 102 at various times. When the data is needed,the host device 102 contacts the memory system 104 to obtain the data.The controller 106 controls the communication between the memory system104 and the host device 102.

The memory system 104 includes a memory controller 108 and multipleCPUs. A first or main CPU 110 is present as are one or more additionalCPUs 112A-112N. The first CPU 110 is the main CPU for interacting withthe host device 102 as will be discussed below. The memory system 104also includes a memory device 114. The memory device 114 is coupled toall of the CPUs 110, 112A-112N as well as the memory controller 108. Inone embodiment, the memory device 114 is a NAND storage device. Inanother embodiment, the memory device 114 is a HDD storage device. It isto be understood that the memory device 114 is not to be limited toeither a NAND storage device or a HDD storage device. Rather, the memorydevice 114 is applicable to any storage device capable of storing datathat may be retrieved by one or more CPUs.

FIGS. 2A and 2B are schematic illustrations of CPUs of the system 100 ofFIG. 1. In FIG. 2A, the first CPU 110 is shown to have a controller 202Athat interacts with both a cache storage 204A and the memory device 114.Similarly, in FIG. 2B, the other CPUs 112A-112N represented by CPU 112all have a controller 202B that interacts with both a cache storage 204Band the memory device 114.

The controllers 106, 202A, 202B are digital circuits that manage theflow of data going to and from the memory system 104 (in the case ofcontroller 106) and to and from an individual CPU 110, 112A-112N (in thecase of controllers 202A, 202B). The controllers 106, 202A, 202B can beseparate chips or integrated into other chips, such as being placed onthe same die or as an integral part of a CPU (as in the case ofcontrollers 202A, 202B). Controllers 106, 202A, 202B may be referred toas integrated memory controllers (IMC), a memory chip controller (MCC)or a memory controller unit (MCU). Additionally, the controllers 106,202A, 202B function to determine an amount of LBNs to prefetch and tocause the amount of LBNs to be prefetched and written into cache.Controller 202A also is able to receive a request from the host device102 and prefetch LBNs from at least one additional CPU 112A-112N.Controllers 202B are able to send prefetched LBNs to the first or mainCPU 110. Controller 202A is able to receive the prefetched LBNs fromcontrollers 202B.

In order to obtain the desired data at the host device 102 from thememory system 104, a prefetching algorithm is utilized. The algorithmuses as much of the memory reserved for read caching as possible. Themore reads that can be serviced from a single processor, the more timeother processors have to refill their read cache before they need toservice reads again. The algorithm tries to have a contiguous range ofLBNs prefetched across all CPUs. If there is an LBN that is notprefetched, the host command that needs to use the LBN will be sloweddown significantly waiting to read that single LBN from NAND or a diskcompared to reading all the data from the cache. The algorithm avoidsthe issue of a single LBN that is needed by different commands targetedat different processors.

To understand the algorithm, a few labels will now be explained.MaxReadLBNsInCache is a constant representing the maximum number of LBNsthat can be stored in the cache of a single processor. NumLBAsPerLBN isa constant representing the number of LBAs in an LBN. LastLBAPrefetchedis the last LBA prefetched on any processor. If no LBAs have beenprefetched yet, then LastLBAPrefetched is the last LBA read by the hostdevice. CmdLen is the number of LBAs prefetched to be read by eachsequential read request the host device is expected to make. In allcases, the first LBN to prefetch (FirstLBNToPrefetch) on a specificprocessor is the next LBN following the LastLBAPrefetched.

If the next LBA to prefetch starts at an LBN boundary, then thecalculation is relatively easy. The minimum number of LBNs that can beadded to cache and still allow all commands to be serviced from a singleprocessor (MinLBNsToAddToCache) is simply the least common multiple ofCmdLen and NumLBAsPerLBN divided by NumLBAsPerLBN. The total number ofLBNs that should be cached is the largest multiple ofMinLBNsToAddToCache that is less than or equal to MaxReadLBNsInCache.

FIG. 3 is a flowchart illustrating a method 300 according to oneembodiment. In the method, the host device 102 initially sends a readrequest to the memory device 104. Specifically, the read request isreceived by the first or main CPU 110 in block 302. The read request isfor data contained in specific LBAs that are contained in one or moreLBNs. A determination is made as to whether the requested data isalready present in cache. More specifically, a determination is made asto whether the requested data is in the cache of the first or main CPU110 in block 304. If the requested data is in the cache of the first ormain CPU 110 as shown by the yes determination in block 306, then thedata is delivered to the host device 102 in block 308. If the data isnot in the cache of the first or main CPU 110 as shown by the nodetermination in block 306, then the data is read from appropriate NAND(or disk in the case of a disk system) in block 310.

Starting at time zero, there will be no data in cache and thus, theinitial read request from the host device will necessitate reading thedata from NAND (or disk), which takes time. During (or even after) theread request processing, non-requested data can begin to be read fromNAND (or disk) block 312 and stored into cache. The read data is sent tothe cache of the first or main CPU 110 in block 314 if the data is notalready in the first or main CPU 110 NAND (or disk). The non-requesteddata is prefetched data that is predicted to be used based upon thealgorithm discussed above. After sufficient iterations, sufficient datawill be in the first or main CPU 110 cache so that the read latency willbe reduced over the situation of reading the data directly from NAND (ordisk) or from multiple caches.

If the data is considered in portions (i.e., LBAs of LBNs), then ingeneral, after the first read request is received, a second request isreceived from the host device to read second LBA data in block 316. Forthe second request, a first portion of the second LBA data is disposedin a first LBN and a second portion of the second LBA data is disposedin a second LBN. The first portion and the second portion are read fromthe memory device 114. The LBN containing the first portion and the LBNfrom the second portion are written to the cache 204A. The data is thenread from the cache 204A and delivered to the host device 102.Additional requests can be handled in a similar manner with the goal ofhaving all of the requested data already in the cache 204A by the timethe host device 102 makes the request. For the second read request,ideally, the reading from memory device 114 and writing to cache 204Awill occur prior to receiving the read request.

FIG. 4 is a flowchart illustrating a method 400 according to anotherembodiment. In the method of FIG. 4, a determination is initially madeto prefetch data in block 402. A determination is then made in block 404regarding whether the LBA data to be prefetched begins and ends on anLBN boundary. If the answer is yes, then the LBN data is read from thememory device 114 in block 406, written to the cache of the main CPU 110in block 408.

If the next LBA to prefetch does not start at an LBN boundary (i.e., theanswer is “no” in block 404), the calculation is more difficult. First,a determination is made regarding how many additional read commands arenecessary before the read command ended on an LBN boundary(NumCmdsToLBNBoundary) in block 410. The number of whole LBNs that areneeded to be cached to handle the number of commands (InitLBNToCache) iscalculated in block 412. From there, InitLBNToCache is subtracted fromthe number of MaxReadLBNsInCache to determine the remaining LBNs thatcould be fit into cache (FreeLBNsInCache) in block 414. ReplacingMaxReadLBNsInCache with MaxRemainingReadLBNsInCache from above, thealgorithm can be used to calculate how many additional LBNs can be readinto cache (AdditionalLBNsInCache) in block 416. The total number ofLBNs to prefetch is the sum of NumWholeLBNsToReachLBNBoundary andNumAdditionalLBNsInCache and is finally prefetched in block 418.

In some cases, it is possible that there is no value forMinLBAsToAddToCache that is small enough to fit in cache. The simplestexample is a sequential read that is always NumLBAsPerLBN long but doesnot start at an LBN boundary. In these cases, it is impossible to avoidthe situation where some specific LBN will need to be read by multipleprocessors, and a best case effort will need to be made instead. In thiscase, the total number of LBNs to prefetch is the number of wholecommands that can be serviced without going over the maximum size of theread cache.

The algorithm can be easily distilled into the following equations:

FirstLBNtoPrefetch=LastLBAPrefetched/(NumLBAsPerLBN+1).

MinLBNsToAddToCache=LCM(CmdLEN,NumLBAsPerLBN)/NumLBAsPerLBN.

NextLBAToPrefetch=LastLBAPrefetched+1.

If (NextLBAToPrefetch) mod NumLBAsPerLBN=0, thenNumLBNsToCache=MaxReadLBNsInCache round down to the nearest multiple ofMinLBNsToAddToCache else solve((NextLBAToPrefetch+NumCmdsToLBNBoundary*CmdLen) mod NumLBAsPerLBN=0 forNumCmdsToLBNBoundary.

InitLBNsToCache=NumCmdsToLBNBoundary*CmdLen/NumLBAsPerLBN.

FreeLBNsInCache=MaxReadLBNsInCache−InitLBNsToCache.

AdditionalLBNsToCache=FreeLBNsInCache rounded down to the nearestmultiple of MinLBNsToAddToCache.

NumLBNsToCache=InitLBNsToCache+AdditionalLBNsToCache.

If NumLBNsToCache=0, thenLeadingLBAsNotInCache=FirstLBNToPrefetch/(NumLBAsPerLBN−NextLBAToPrefetch).

NumCmdsFromCache=(MaxReadLBNsInCache*(NumLBAsPerLBN+LeadingLBAsNotInCache))/CmdLen.

NumLBNsToCache=(NumCmdsFromCache*(CmdLen−LeadingLBAsNotInCache))/NumLBAsPerLBN.

LastLBAPrefetched=NumCmdsFromCache*CmdLen elseLastLBAPrefetched=(FirstLBNToPrefetch+NumLBNsToCache)*NumLBAsPerLBN−1.

When prefetching data from NAND or disk, it is possible that theexpected host command to read that data starts being processed beforethe prefetch is complete and the data has been added to the read cache.In this situation, if the host command is continued as normal, the datawill not be found in cache and will be treated as a normal read. Thiscreates two problems. First, the drive spent unnecessary timeprefetching data from NAND or disk that will eventually get thrown away.Second, depending on how far along the prefetch command processing is,there may be a read collision between the prefetch command and the hostcommand which will cause additional overhead for the hose command. Apotential solution to the problem is, during host read processing, ifthe drive detects a prefetch command for the same LBN as in the hostread is in process, it stalls processing the host command until theprefetch command completes. This is not preferable however, as there maybe subsequent LBNs in the same host command that are not in or pendingto be added to the read cache. If the host command is not stalled, readson LBNs not scheduled to be prefetched can be executed in parallel withthe prefetch commands, which results in an overall faster execution timefor the host command.

Reserving space in the cache for a pending read to cache operation toprevent a subsequent host read request from reading the same LBN, whileallowing subsequent LBN reads as part of the same host read request willnow be discussed with regards to the method 500 shown in FIG. 5.

When a prefetch command is first issued in block 502, temporaryplaceholds are added to the read cache for each LBN in the prefetchcommand indicating that the read to cache is pending in block 504. Whena host read command that was anticipated by the prefetching enginestarts being processed, for each LBN in the command, the processorchecks if the LBN is in cache or not in block 506 to determine if theLBN is in cache, not in cache, or pending in cache. If the LBN hasalready completed being read into cache, the processor continuesprocessing the LBN as if the LBN had just been read from NAND or disk inblock 508. If the LBN is not in cache, the processor initiates a newread request from NAND or disk for that LBN in block 510. If theprocessor finds that the LBN read to cache is pending, then a copy ofthe context associated with the LBN is associated with the host readcommand in block 512 and added to a list of LBN contexts that is waitingfor a read to cache to complete in block 514. This processing continuesuntil all LBNs in the host command have been processed or a new readfrom NAND or disk being issued due to the LBN not found in cache.

When a pending read to cache completes for a given LBN in block 516, theprocessor will look for a matching LBN context in the pending list inblock 518. If a match is found, the data is linked to the host commandin block 520, the host command is continued as if the LBN had just beenread from NAND or disk, and the entry is removed from cache in block522. If no match is found, the LBN data is left in cache waiting for ahost command to read it.

One problem that can result from the algorithm is the issue of LBNs incollision. Specifically, there are two issues that can occur. The firstis that an LBN being prefetched into cache detects a collision and ahost command is currently waiting for that LBN. The second is an LBNbeing read from NAND by the host command has read subsequent LBNs infrom cache. In both of these cases, there is a possibility of deadlockbetween the command that holds the lock for the LBN in collision and anylocks this host command holds for subsequent LBNs. The processor needsto iterate through all subsequent LBNs in this host command and releasethem. Once the collision on the current LBN is resolved, the subsequentLBNs can be re-requested.

Overall, by prefetching LBNs, which contain LBAs, and storing the datainto cache of a single processor will reduce the read latency for a readrequest from a host device. Caching LBN data into cache of a singleprocessor reduces any need to read data from NAND or from additionalprocessors upon receiving the read request. As a result, the latency isonly between receiving the read request from the host device anddelivering the read from cache in a single processor. The prefetchingmay occur by obtaining the LBNs from a single CPU or multiple CPUs andstoring the prefetched data in a single CPU in the single CPU's cache.Alternatively, the prefetching may occur by obtaining the LBNs frommultiple CPUs and consolidating (by storing) all of the prefetched dataon a single CPU in the single CPU's cache.

While the foregoing is directed to embodiments of the presentdisclosure, other and further embodiments of the disclosure may bedevised without departing from the basic scope thereof, and the scopethereof is determined by the claims that follow.

What is claimed is:
 1. A system, comprising: a memory system, the memorysystem comprising: a first CPU; at least one additional CPU; a memorydevice coupled to both the first CPU and the at least one additionalCPU; and a controller coupled to the memory system, the controllerconfigured to: receive a first request from a host device to read afirst data and a second request to read a second data from a memorydevice that is coupled to a plurality of CPUs, wherein a first CPU ofthe plurality of CPUs has a first cache storage and a second CPU of theplurality of CPUs has a second cache storage; read the first data fromthe memory device using the first CPU; read the second data from thememory device using the second CPU of the plurality of CPUs; write thefirst data and the second data to the first cache storage of the firstCPU; read the first and second data from the first cache storage; anddeliver the first and second data to the host device.
 2. The system ofclaim 1, wherein the memory device is a NAND storage device.
 3. Thesystem of claim 1, wherein the memory device is a hard disk drivestorage device.
 4. A system of claim 1, wherein the controller isfurther configured to: receive a second request from a host device toread a first LBA data from a first LBN and a second LBN disposed in thememory device that is coupled to the first CPU and the second CPU,wherein the first CPU has a first cache storage and is assigned thefirst_LBN, wherein the second CPU has a second cache storage and isassigned the second LBN; read a first portion of the first LBA data fromthe first LBN of the memory device; read a second portion of the firstLBA data from the second LBN of the memory device; write the firstportion of the first LBN data and the second portion of the first LBNdata to the first cache storage; read the first LBA data from the firstcache storage; and deliver the first LBA data to the host device.
 5. Thesystem of claim 4, wherein the controller is further configured to:receive a third request from the host device to read a second LBA datafrom the memory device, wherein the first LBA data and the second LBAdata are sequential data; read the second LBA data from the memorydevice; write the second LBA data to the first cache storage; anddeliver the second LBA data to the host device.
 6. The system of claim5, wherein the writing the second LBA data to the first cache storageoccurs prior to receiving the second request.
 7. The system of claim 4,wherein the reading the first portion of the first LBA data is performedby the first CPU and reading the second portion of the first LBA data isperformed by the second CPU.
 8. The system of claim 1, wherein thecontroller is configured to determine whether the first data is disposedin the first cache storage.
 9. The system of claim 8, wherein thecontroller is configured to deliver the first data to a host device upondetermining that the first data is in the first cache storage.
 10. Thesystem of claim 9, wherein the controller is further configured to readthe first data from the first cache storage.
 11. The system of claim 8,wherein the controller is configured to read the first data from thememory device upon determining that the first data is not disposed inthe first cache storage.
 12. The system of claim 11, wherein thecontroller is configured to write the first data into the first cachestorage.
 13. The system of claim 12, wherein the controller isconfigured to deliver the first data to a host device from the firstcache storage.
 14. The system of claim 1, wherein the controller isconfigured to prefetch LBA data.
 15. The system of claim 14, wherein thecontroller is configured to determine whether the LBA data begins andends on LBN boundaries.
 16. The system of claim 15, wherein thecontroller is configured to read LBA data from the memory device upondetermining that the LBA data begins and ends on the LBN boundaries. 17.The system of claim 16, wherein the controller is configured to writethe LBA data to the first cache storage.
 18. The system of claim 15,wherein the controller is configured to determine how many additionalread commands are necessary for the LBA data to end on a LBN boundaryupon determining that the LBA data does not being and end on the LBNboundaries.
 19. The system of claim 18, wherein the controller isconfigured to calculate a number of whole LBNs that are needed to becached to handle the determined additional read commands.
 20. The systemof claim 19, wherein the controller is configured to determine remainingLBNs that could be fit into the first cache storage.